Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae8e75a2d1050899e77895b6342747ce32320a9ca7b9932295580d67d00b8f9

Tx prefix hash: 141997e7847f75b7153510fc8eb5a5386c898913348025c831aef69c7ec2c01d
Tx public key: c021e399acec82db785bad30bab47c0f88449f6ba3094502c1b76565b8c991a5
Timestamp: 1578421165 Timestamp [UCT]: 2020-01-07 18:19:25 Age [y:d:h:m:s]: 05:067:21:34:07
Block: 40710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198519 RingCT/type: yes/0
Extra: 01c021e399acec82db785bad30bab47c0f88449f6ba3094502c1b76565b8c991a50211000000032264afe6000000000000000000

1 output(s) for total of 449.895570272000 dcy

stealth address amount amount idx
00: 381bb47f88f88a2e2edb6bab1d1664df9a65c4611cb526995277191ac7c33eec 449.895570272000 71762 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": 40720, "vin": [ { "gen": { "height": 40710 } } ], "vout": [ { "amount": 449895570272, "target": { "key": "381bb47f88f88a2e2edb6bab1d1664df9a65c4611cb526995277191ac7c33eec" } } ], "extra": [ 1, 192, 33, 227, 153, 172, 236, 130, 219, 120, 91, 173, 48, 186, 180, 124, 15, 136, 68, 159, 107, 163, 9, 69, 2, 193, 183, 101, 101, 184, 201, 145, 165, 2, 17, 0, 0, 0, 3, 34, 100, 175, 230, 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