Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bec1aa487157877318f2a3334f9c0b9d063d8393bec36f1f9971f944d8c96da

Tx prefix hash: 01086e81d0a6a904ba0c2c6eff8ee4b955ff834076d49c0ed764da7c5d08a9be
Tx public key: 177d10d8e283b0ed1b31861fb6c60e29b8aff6801886653fada6d2d5f69e2209
Timestamp: 1709315343 Timestamp [UCT]: 2024-03-01 17:49:03 Age [y:d:h:m:s]: 01:028:02:00:52
Block: 968987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281064 RingCT/type: yes/0
Extra: 01177d10d8e283b0ed1b31861fb6c60e29b8aff6801886653fada6d2d5f69e220902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e84eb6b558bef487ff6c3ffc2cd4ce02924cab30f39d525f46145426b624798 0.600000000000 1428814 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": 968997, "vin": [ { "gen": { "height": 968987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e84eb6b558bef487ff6c3ffc2cd4ce02924cab30f39d525f46145426b624798" } } ], "extra": [ 1, 23, 125, 16, 216, 226, 131, 176, 237, 27, 49, 134, 31, 182, 198, 14, 41, 184, 175, 246, 128, 24, 134, 101, 63, 173, 166, 210, 213, 246, 158, 34, 9, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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