Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9578eca4b6d7cc61397c59cc137dd3038c4989027dcbcbcf8bde05c184b51e4

Tx prefix hash: 34b1f15c9c11959f35067868b7eb20733c1c3dfaaa523a4b3008a620a8b2d678
Tx public key: 77e19fef964dcab8887cf62263ffd951f46563f3073a92df699d4d309a954d00
Timestamp: 1700473588 Timestamp [UCT]: 2023-11-20 09:46:28 Age [y:d:h:m:s]: 01:154:08:37:41
Block: 895677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371495 RingCT/type: yes/0
Extra: 0177e19fef964dcab8887cf62263ffd951f46563f3073a92df699d4d309a954d0002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.661074303000 dcy

stealth address amount amount idx
00: dc81ff4082f0c2f4e56a545c763a0a406f151ac390cfb8bac8f7f9e1ab0f0f5f 0.661074303000 1351918 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": 895687, "vin": [ { "gen": { "height": 895677 } } ], "vout": [ { "amount": 661074303, "target": { "key": "dc81ff4082f0c2f4e56a545c763a0a406f151ac390cfb8bac8f7f9e1ab0f0f5f" } } ], "extra": [ 1, 119, 225, 159, 239, 150, 77, 202, 184, 136, 124, 246, 34, 99, 255, 217, 81, 244, 101, 99, 243, 7, 58, 146, 223, 105, 157, 77, 48, 154, 149, 77, 0, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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