Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c845dbce5c4d9d5f68b3b50dc842cf9c356b1b4ae32d54e698886411035021d1

Tx prefix hash: 7ee3e4b20217942c77342cec0b0ce296765e2ee071ec101c82cf11ee7e0bab1e
Tx public key: 215098e7dddc276d9528d9bc329b5a1065f470e90d749e75741da358bbe70991
Timestamp: 1575883126 Timestamp [UCT]: 2019-12-09 09:18:46 Age [y:d:h:m:s]: 05:326:20:07:34
Block: 24009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1376993 RingCT/type: yes/0
Extra: 01215098e7dddc276d9528d9bc329b5a1065f470e90d749e75741da358bbe70991021100000007ad433a0b000000000000000000

1 output(s) for total of 511.033166866000 dcy

stealth address amount amount idx
00: c87c06d9b07b284da92e38c038f74cdccf66aa22f516d4efe454ffb541a748f2 511.033166866000 38922 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": 24019, "vin": [ { "gen": { "height": 24009 } } ], "vout": [ { "amount": 511033166866, "target": { "key": "c87c06d9b07b284da92e38c038f74cdccf66aa22f516d4efe454ffb541a748f2" } } ], "extra": [ 1, 33, 80, 152, 231, 221, 220, 39, 109, 149, 40, 217, 188, 50, 155, 90, 16, 101, 244, 112, 233, 13, 116, 158, 117, 116, 29, 163, 88, 187, 231, 9, 145, 2, 17, 0, 0, 0, 7, 173, 67, 58, 11, 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