Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f02d2b640c3cef986268cddbb0444e71e032c47869a4d9bc63c30c29cbd66b

Tx prefix hash: 7c8ca4f570ba9a2f59828318ea706492930f234f34f98b7a3b5e856532c00324
Tx public key: 7bd5ff6d57c3d4777766fa09b655831b3fce20b2c86f0be1d6db9a2aa8048000
Timestamp: 1695479396 Timestamp [UCT]: 2023-09-23 14:29:56 Age [y:d:h:m:s]: 01:249:01:01:48
Block: 854467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439102 RingCT/type: yes/0
Extra: 017bd5ff6d57c3d4777766fa09b655831b3fce20b2c86f0be1d6db9a2aa804800002110000000733af99f4000000000000000000

1 output(s) for total of 0.905307614000 dcy

stealth address amount amount idx
00: f18456f335d7e54515cb78d9ffc02f2965b90872088ee344bfbec9876b2a3b0d 0.905307614000 1308441 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": 854477, "vin": [ { "gen": { "height": 854467 } } ], "vout": [ { "amount": 905307614, "target": { "key": "f18456f335d7e54515cb78d9ffc02f2965b90872088ee344bfbec9876b2a3b0d" } } ], "extra": [ 1, 123, 213, 255, 109, 87, 195, 212, 119, 119, 102, 250, 9, 182, 85, 131, 27, 63, 206, 32, 178, 200, 111, 11, 225, 214, 219, 154, 42, 168, 4, 128, 0, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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