Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc44b86640480018217fcc1ede85aecd69c6d8e432555f2c6ef5693e662358b5

Tx prefix hash: 290822bcd02046d9a9d1e8678e0660ad9b8380e5e0189f43e9ddbaf05550c019
Tx public key: dfa374eec1b3acb0be2baffd9a47fccf071ad7038d6a41a9c57e1fb7074190f4
Timestamp: 1730955972 Timestamp [UCT]: 2024-11-07 05:06:12 Age [y:d:h:m:s]: 00:137:07:18:46
Block: 1148298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97953 RingCT/type: yes/0
Extra: 01dfa374eec1b3acb0be2baffd9a47fccf071ad7038d6a41a9c57e1fb7074190f4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db009db8842d7641b9b1f47245277eacb95251c4cbde479d09f9025404539608 0.600000000000 1633107 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": 1148308, "vin": [ { "gen": { "height": 1148298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db009db8842d7641b9b1f47245277eacb95251c4cbde479d09f9025404539608" } } ], "extra": [ 1, 223, 163, 116, 238, 193, 179, 172, 176, 190, 43, 175, 253, 154, 71, 252, 207, 7, 26, 215, 3, 141, 106, 65, 169, 197, 126, 31, 183, 7, 65, 144, 244, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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