Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d90f9ffb3ab4c80598bb7c8c72ad6b234cb85a38b419a8ff539bebfd019e6103

Tx prefix hash: 75a83bf068588cffad4caf5e525f57c05cd963fae95606be7426982d2618d23c
Tx public key: 0ce9f0d23a504fa387163a1b9fe982978900d104f8fbcecf6246292d1967e4c5
Timestamp: 1725751503 Timestamp [UCT]: 2024-09-07 23:25:03 Age [y:d:h:m:s]: 00:209:15:43:53
Block: 1105240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149675 RingCT/type: yes/0
Extra: 010ce9f0d23a504fa387163a1b9fe982978900d104f8fbcecf6246292d1967e4c502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7bfa12d8a2e79f40b56d12a5bd55e7af38e7fe2ec1f45b8000fd92dc23d036e 0.600000000000 1582579 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": 1105250, "vin": [ { "gen": { "height": 1105240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7bfa12d8a2e79f40b56d12a5bd55e7af38e7fe2ec1f45b8000fd92dc23d036e" } } ], "extra": [ 1, 12, 233, 240, 210, 58, 80, 79, 163, 135, 22, 58, 27, 159, 233, 130, 151, 137, 0, 209, 4, 248, 251, 206, 207, 98, 70, 41, 45, 25, 103, 228, 197, 2, 17, 0, 0, 0, 6, 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