Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9f82979ca3ae52b5fd7fbe38db791940b99bf7ace3c25cf2984838e8b179f5

Tx prefix hash: b298d45c177fea223810cde34e3670a94c1f1de3481351c48a989c2e41f5254e
Tx public key: e174aef4c3df2a399ff85920e71ff417542c067231c81648908f75817a4dc6b0
Timestamp: 1649486181 Timestamp [UCT]: 2022-04-09 06:36:21 Age [y:d:h:m:s]: 02:276:06:19:40
Block: 476375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717235 RingCT/type: yes/0
Extra: 01e174aef4c3df2a399ff85920e71ff417542c067231c81648908f75817a4dc6b002110000000137cb3088000000000000000000

1 output(s) for total of 16.202329999000 dcy

stealth address amount amount idx
00: fc735f13591a4eda98aeda6205e1c7982db22b7dc3e5b6059125d82c63e4c525 16.202329999000 896828 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": 476385, "vin": [ { "gen": { "height": 476375 } } ], "vout": [ { "amount": 16202329999, "target": { "key": "fc735f13591a4eda98aeda6205e1c7982db22b7dc3e5b6059125d82c63e4c525" } } ], "extra": [ 1, 225, 116, 174, 244, 195, 223, 42, 57, 159, 248, 89, 32, 231, 31, 244, 23, 84, 44, 6, 114, 49, 200, 22, 72, 144, 143, 117, 129, 122, 77, 198, 176, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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