Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eba77b81355ef44d861116f8bdc63336e5080ec9d1696f245869fa26b8d9936

Tx prefix hash: 9e93fafbe24a6403ad1cd85cf5bd6dad846762e8e59bf525d36c37c6bedbd795
Tx public key: 6df7e5eaa254983e0e85bbc15c4ad08076d139e92fdd6dc5007e4c5d3ccf1b34
Timestamp: 1630814957 Timestamp [UCT]: 2021-09-05 04:09:17 Age [y:d:h:m:s]: 03:186:10:48:27
Block: 327713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 907894 RingCT/type: yes/0
Extra: 016df7e5eaa254983e0e85bbc15c4ad08076d139e92fdd6dc5007e4c5d3ccf1b3402110000000a51fa4013000000000000000000

1 output(s) for total of 50.367598074000 dcy

stealth address amount amount idx
00: 16bf2917cb6004e56a2a494e1ea77ea30ecd2ce1d8287e1af5bb0c6c6f97d340 50.367598074000 678616 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": 327723, "vin": [ { "gen": { "height": 327713 } } ], "vout": [ { "amount": 50367598074, "target": { "key": "16bf2917cb6004e56a2a494e1ea77ea30ecd2ce1d8287e1af5bb0c6c6f97d340" } } ], "extra": [ 1, 109, 247, 229, 234, 162, 84, 152, 62, 14, 133, 187, 193, 92, 74, 208, 128, 118, 209, 57, 233, 47, 221, 109, 197, 0, 126, 76, 93, 60, 207, 27, 52, 2, 17, 0, 0, 0, 10, 81, 250, 64, 19, 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