Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49bdc472391cabc1280fc523d61abf2d2b61a8a684b3386a6fb95b5a5819883b

Tx prefix hash: ff49392abf89234a23dfa044426907656dcf93f7b3afa9958a0ed32d3ab8a825
Tx public key: dff25539bbf1b9a053c2cb70832908bce85b8695db940fdbbc9c1517b3abf347
Timestamp: 1722443029 Timestamp [UCT]: 2024-07-31 16:23:49 Age [y:d:h:m:s]: 00:249:06:03:49
Block: 1077806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178033 RingCT/type: yes/0
Extra: 01dff25539bbf1b9a053c2cb70832908bce85b8695db940fdbbc9c1517b3abf34702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c3cadd743e47f11b9ff84bd7aa287ec435c65b869040d0e554ea69b01a9ebe 0.600000000000 1550361 of 15

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": 1077816, "vin": [ { "gen": { "height": 1077806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c3cadd743e47f11b9ff84bd7aa287ec435c65b869040d0e554ea69b01a9ebe" } } ], "extra": [ 1, 223, 242, 85, 57, 187, 241, 185, 160, 83, 194, 203, 112, 131, 41, 8, 188, 232, 91, 134, 149, 219, 148, 15, 219, 188, 156, 21, 23, 179, 171, 243, 71, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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