Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ced993e2dab8591e2c3e4ed12efe91a2a45315b7ded7ee27706b75034ea4234a

Tx prefix hash: 85dd97118614691d87ac61d0d7db87347614ac4adbf11079944f491e543ab9fa
Tx public key: c2d1b0470f3c8d3bf9981b3f7fce0d8d20004bc36b17d506677a9679754cd02d
Timestamp: 1677626366 Timestamp [UCT]: 2023-02-28 23:19:26 Age [y:d:h:m:s]: 02:038:14:38:45
Block: 707137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549172 RingCT/type: yes/0
Extra: 01c2d1b0470f3c8d3bf9981b3f7fce0d8d20004bc36b17d506677a9679754cd02d021100000001835e4d22000000000000000000

1 output(s) for total of 2.785874033000 dcy

stealth address amount amount idx
00: 3aa17882b92838ffa3ad40f303f0a6e4d74204a6a856104424229e7b00f001d5 2.785874033000 1150934 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": 707147, "vin": [ { "gen": { "height": 707137 } } ], "vout": [ { "amount": 2785874033, "target": { "key": "3aa17882b92838ffa3ad40f303f0a6e4d74204a6a856104424229e7b00f001d5" } } ], "extra": [ 1, 194, 209, 176, 71, 15, 60, 141, 59, 249, 152, 27, 63, 127, 206, 13, 141, 32, 0, 75, 195, 107, 23, 213, 6, 103, 122, 150, 121, 117, 76, 208, 45, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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