Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40513c3def4a61d14713374e33bec04037db41cd21a1a07907a9d8af4e7f78df

Tx prefix hash: 76d136314bafe29d0cfaa11922251b238a2bb7294bf1a49deea989ea4df59d1b
Tx public key: 1ed127b7811d0d9b2e8ee8531d78246810036385f9d377120813235ceeeb9faa
Timestamp: 1578079796 Timestamp [UCT]: 2020-01-03 19:29:56 Age [y:d:h:m:s]: 05:011:14:48:20
Block: 37940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158456 RingCT/type: yes/0
Extra: 011ed127b7811d0d9b2e8ee8531d78246810036385f9d377120813235ceeeb9faa0211000002a1597126dd000000000000000000

1 output(s) for total of 459.504618661000 dcy

stealth address amount amount idx
00: 7c0077389283cbee2b7de690501cd741437d224bb2e160ba228c0d9e5ddd6ae4 459.504618661000 64517 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": 37950, "vin": [ { "gen": { "height": 37940 } } ], "vout": [ { "amount": 459504618661, "target": { "key": "7c0077389283cbee2b7de690501cd741437d224bb2e160ba228c0d9e5ddd6ae4" } } ], "extra": [ 1, 30, 209, 39, 183, 129, 29, 13, 155, 46, 142, 232, 83, 29, 120, 36, 104, 16, 3, 99, 133, 249, 211, 119, 18, 8, 19, 35, 92, 238, 235, 159, 170, 2, 17, 0, 0, 2, 161, 89, 113, 38, 221, 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