Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60fb0839072a255ec77f2e429e40e52aacc3c98851cf467168c5556ef05a771

Tx prefix hash: 1b73149903d1ac1874ff788038c0454e6e54a0781148df3714cfca97af0fde95
Tx public key: 8c474b7999efc6a03f4c2d6e51d84ab4befdc60f78030bb0e40d9ffd736d2e9c
Timestamp: 1737296507 Timestamp [UCT]: 2025-01-19 14:21:47 Age [y:d:h:m:s]: 00:150:21:57:13
Block: 1200762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107576 RingCT/type: yes/0
Extra: 018c474b7999efc6a03f4c2d6e51d84ab4befdc60f78030bb0e40d9ffd736d2e9c021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b074dd35a266d65f65c2f43eb133f5926497a203cb22bf45b5f77bcc0821736 0.600000000000 1687407 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": 1200772, "vin": [ { "gen": { "height": 1200762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b074dd35a266d65f65c2f43eb133f5926497a203cb22bf45b5f77bcc0821736" } } ], "extra": [ 1, 140, 71, 75, 121, 153, 239, 198, 160, 63, 76, 45, 110, 81, 216, 74, 180, 190, 253, 198, 15, 120, 3, 11, 176, 228, 13, 159, 253, 115, 109, 46, 156, 2, 17, 0, 0, 0, 8, 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