Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f403153ad424abbdadc72974d6512b8cff9f49d2591fd74c58a5b2261073e002

Tx prefix hash: 38f839b597d97ec189f4566db3a110fe77533be8f23c901c3f6b3013bc1c1faf
Tx public key: a358662b9505f571ad6b2589dfce2b0558c90721c6d0e11c73b96fec6d1ef6d9
Timestamp: 1737814716 Timestamp [UCT]: 2025-01-25 14:18:36 Age [y:d:h:m:s]: 00:255:06:33:40
Block: 1205055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179918 RingCT/type: yes/0
Extra: 01a358662b9505f571ad6b2589dfce2b0558c90721c6d0e11c73b96fec6d1ef6d9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80f23a7a889e37db73bdc0c807d935915bd39b2c8a76e4b9e2fcf4746835901b 0.600000000000 1691752 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1205065, "vin": [ { "gen": { "height": 1205055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80f23a7a889e37db73bdc0c807d935915bd39b2c8a76e4b9e2fcf4746835901b" } } ], "extra": [ 1, 163, 88, 102, 43, 149, 5, 245, 113, 173, 107, 37, 137, 223, 206, 43, 5, 88, 201, 7, 33, 198, 208, 225, 28, 115, 185, 111, 236, 109, 30, 246, 217, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8