Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a29e37cd713479399d8c72fdc98784c93de786e085b007fb80feb3b08d6d84

Tx prefix hash: c88e58d19bb1a990c28641ca2bee52698a88322fb82e6749bb634ebf7bf4e28c
Tx public key: a017f6e85e3375e8622ad81900cc0e2100876d44b92197557b4866e4d2f162bc
Timestamp: 1620396252 Timestamp [UCT]: 2021-05-07 14:04:12 Age [y:d:h:m:s]: 04:024:23:07:01
Block: 256030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038912 RingCT/type: yes/0
Extra: 01a017f6e85e3375e8622ad81900cc0e2100876d44b92197557b4866e4d2f162bc0211000001e57071732b000000000000000000

1 output(s) for total of 87.029578066000 dcy

stealth address amount amount idx
00: f86f8b70000f71fdccffd2fb4cf643659761774d305890c4cad0b3a7b91b10ae 87.029578066000 538505 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": 256040, "vin": [ { "gen": { "height": 256030 } } ], "vout": [ { "amount": 87029578066, "target": { "key": "f86f8b70000f71fdccffd2fb4cf643659761774d305890c4cad0b3a7b91b10ae" } } ], "extra": [ 1, 160, 23, 246, 232, 94, 51, 117, 232, 98, 42, 216, 25, 0, 204, 14, 33, 0, 135, 109, 68, 185, 33, 151, 85, 123, 72, 102, 228, 210, 241, 98, 188, 2, 17, 0, 0, 1, 229, 112, 113, 115, 43, 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