Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e226a74f627914e1821e96af6ea9fc4db7d606a368d1815862c0aeb3a380ff

Tx prefix hash: 894c68cd7f3e0d22588bfefb6b417f0d4e949354163dafe98b8160fe389cc0e2
Tx public key: b172102f9e929c3acfef6d18b8860201468856f1e570f8bf01e60c7236cd67e1
Timestamp: 1694651634 Timestamp [UCT]: 2023-09-14 00:33:54 Age [y:d:h:m:s]: 01:258:01:29:41
Block: 847585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445586 RingCT/type: yes/0
Extra: 01b172102f9e929c3acfef6d18b8860201468856f1e570f8bf01e60c7236cd67e1021100000006faf35c9c000000000000000000

1 output(s) for total of 0.954111446000 dcy

stealth address amount amount idx
00: 6affded0fa53ba3be5c7b8f58fad65c6ee84a83871944f49c879e7a0c6932371 0.954111446000 1301119 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": 847595, "vin": [ { "gen": { "height": 847585 } } ], "vout": [ { "amount": 954111446, "target": { "key": "6affded0fa53ba3be5c7b8f58fad65c6ee84a83871944f49c879e7a0c6932371" } } ], "extra": [ 1, 177, 114, 16, 47, 158, 146, 156, 58, 207, 239, 109, 24, 184, 134, 2, 1, 70, 136, 86, 241, 229, 112, 248, 191, 1, 230, 12, 114, 54, 205, 103, 225, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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