Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d4db213a3bf631661e6e717b7e0b441d6ff78e34339b505c38b7701b07653b

Tx prefix hash: ca88931ab1ef8b45032644c415d2f2596f0fc9dcf0413a052dc700bc88d12e96
Tx public key: 0c7d24453e4b70860dcca907b4048f1ac0e7b140d21f5f5a559e25aaa76f00ea
Timestamp: 1707412619 Timestamp [UCT]: 2024-02-08 17:16:59 Age [y:d:h:m:s]: 01:089:17:42:38
Block: 953189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325214 RingCT/type: yes/0
Extra: 010c7d24453e4b70860dcca907b4048f1ac0e7b140d21f5f5a559e25aaa76f00ea02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af29a39a7e1391639c0ad27f1274b284f3db62b3f904701c7402d1740e847363 0.600000000000 1412367 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": 953199, "vin": [ { "gen": { "height": 953189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af29a39a7e1391639c0ad27f1274b284f3db62b3f904701c7402d1740e847363" } } ], "extra": [ 1, 12, 125, 36, 69, 62, 75, 112, 134, 13, 204, 169, 7, 180, 4, 143, 26, 192, 231, 177, 64, 210, 31, 95, 90, 85, 158, 37, 170, 167, 111, 0, 234, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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