Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9d496478d52d2d1502dde182842b4c5a83a3725eea2b3b84d20c91803cf9b2

Tx prefix hash: 42ae49eb0c28ed46602fa39673a0fe51ca8b59663734410bb23498727ca39af4
Tx public key: fc0005136cc02ff0d1177466aeae95ce715a17a8e16595a8e36c2c805b46f1da
Timestamp: 1710122597 Timestamp [UCT]: 2024-03-11 02:03:17 Age [y:d:h:m:s]: 01:099:06:40:38
Block: 975678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331868 RingCT/type: yes/0
Extra: 01fc0005136cc02ff0d1177466aeae95ce715a17a8e16595a8e36c2c805b46f1da02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bda94e9c1a96fe06b896d3858b6741758671f97aae8096e0ae03a763bf4c8f7 0.600000000000 1435651 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": 975688, "vin": [ { "gen": { "height": 975678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bda94e9c1a96fe06b896d3858b6741758671f97aae8096e0ae03a763bf4c8f7" } } ], "extra": [ 1, 252, 0, 5, 19, 108, 192, 47, 240, 209, 23, 116, 102, 174, 174, 149, 206, 113, 90, 23, 168, 225, 101, 149, 168, 227, 108, 44, 128, 91, 70, 241, 218, 2, 17, 0, 0, 0, 11, 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