Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f2a0f211d644cab34978c58ee0419a1433610e07a476867b5a243c1454bd98

Tx prefix hash: 05f37a36763ce773f705631cbbaace53c40f9c6d0c1489d6552e6274b77e2eb6
Tx public key: 773a4d83dfa44819e424c4b823dabde88d81bdb7673fe444ef43e8e2fdc4d139
Timestamp: 1736902955 Timestamp [UCT]: 2025-01-15 01:02:35 Age [y:d:h:m:s]: 00:154:22:53:09
Block: 1197541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110436 RingCT/type: yes/0
Extra: 01773a4d83dfa44819e424c4b823dabde88d81bdb7673fe444ef43e8e2fdc4d139021100000010007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4b4b84b86a53f8bd506e8f339d706850b157d7de79df9509c46e44d5f98d96 0.600000000000 1684152 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": 1197551, "vin": [ { "gen": { "height": 1197541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4b4b84b86a53f8bd506e8f339d706850b157d7de79df9509c46e44d5f98d96" } } ], "extra": [ 1, 119, 58, 77, 131, 223, 164, 72, 25, 228, 36, 196, 184, 35, 218, 189, 232, 141, 129, 189, 183, 103, 63, 228, 68, 239, 67, 232, 226, 253, 196, 209, 57, 2, 17, 0, 0, 0, 16, 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