Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc2ebcc1e403dd13bd8d874175fd2c393c0336f4f575d827bf3bd6cac179662d

Tx prefix hash: 6b471d269b71e37ed18074d00a009ad6cb2dc8bd4ec0ed159fd6dd18a98354f4
Tx public key: 1bdab2438822a6ae80fc991e8ac0e6c5246a77260f7553aaa9c2f3d2d32aa13c
Timestamp: 1582932427 Timestamp [UCT]: 2020-02-28 23:27:07 Age [y:d:h:m:s]: 04:306:21:37:17
Block: 73679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113015 RingCT/type: yes/0
Extra: 011bdab2438822a6ae80fc991e8ac0e6c5246a77260f7553aaa9c2f3d2d32aa13c0211000000198a2ee0d9000000000000000000

1 output(s) for total of 349.841790118000 dcy

stealth address amount amount idx
00: 01244bf6adfbbae756af12921b5e980f0d9ea04b50e9301c0ae48c7371107484 349.841790118000 135964 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": 73689, "vin": [ { "gen": { "height": 73679 } } ], "vout": [ { "amount": 349841790118, "target": { "key": "01244bf6adfbbae756af12921b5e980f0d9ea04b50e9301c0ae48c7371107484" } } ], "extra": [ 1, 27, 218, 178, 67, 136, 34, 166, 174, 128, 252, 153, 30, 138, 192, 230, 197, 36, 106, 119, 38, 15, 117, 83, 170, 169, 194, 243, 210, 211, 42, 161, 60, 2, 17, 0, 0, 0, 25, 138, 46, 224, 217, 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