Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5405646e692e5ff2f50b971186ff4d5929a2493f2825846c3a7a1d6bc8db72b

Tx prefix hash: b57b52b40aac3449b277f28fd4c07bc95dddefd5f4168156e67094a987c00e61
Tx public key: 9ece322f5fa94f0b61e925ab3655298ab162c4c6f8e71666ff309874b7d1d42c
Timestamp: 1727993084 Timestamp [UCT]: 2024-10-03 22:04:44 Age [y:d:h:m:s]: 00:051:20:44:19
Block: 1123822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37051 RingCT/type: yes/0
Extra: 019ece322f5fa94f0b61e925ab3655298ab162c4c6f8e71666ff309874b7d1d42c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6429daba18fa6321a2062b92bb25820b8702dc0020cf4f3ceab68a5706f212a7 0.600000000000 1606357 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": 1123832, "vin": [ { "gen": { "height": 1123822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6429daba18fa6321a2062b92bb25820b8702dc0020cf4f3ceab68a5706f212a7" } } ], "extra": [ 1, 158, 206, 50, 47, 95, 169, 79, 11, 97, 233, 37, 171, 54, 85, 41, 138, 177, 98, 196, 198, 248, 231, 22, 102, 255, 48, 152, 116, 183, 209, 212, 44, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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