Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623ae3eb47677b9852b52d6c69d4b6c0f10c269274035420ced19733291f8bc1

Tx prefix hash: 3c68812ee3f3f45ffabd8af1296e9f5dc3df4cecee4de2d57f8809166efe4852
Tx public key: f21ccc9b6ad10080a4bb74a2df36e83a2412d671d5074425b74ae438725240a1
Timestamp: 1648348253 Timestamp [UCT]: 2022-03-27 02:30:53 Age [y:d:h:m:s]: 02:324:19:50:33
Block: 467189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 751473 RingCT/type: yes/0
Extra: 01f21ccc9b6ad10080a4bb74a2df36e83a2412d671d5074425b74ae438725240a102110000000137cb3088000000000000000000

1 output(s) for total of 17.378374711000 dcy

stealth address amount amount idx
00: 56cf5a0371bed4dfb3c0403445cf5d1e299c156119c227276e2fe1eee06a7bcb 17.378374711000 885646 of 0

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": 467199, "vin": [ { "gen": { "height": 467189 } } ], "vout": [ { "amount": 17378374711, "target": { "key": "56cf5a0371bed4dfb3c0403445cf5d1e299c156119c227276e2fe1eee06a7bcb" } } ], "extra": [ 1, 242, 28, 204, 155, 106, 209, 0, 128, 164, 187, 116, 162, 223, 54, 232, 58, 36, 18, 214, 113, 213, 7, 68, 37, 183, 74, 228, 56, 114, 82, 64, 161, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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