Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f1ee6a717c479de404c7414b236e19702cd9ce9b8dd84b815e3d2f8d6cc280

Tx prefix hash: 65965951fd9d031e474ab574b8d7044d0e2c38a82abf2a34f9a9071a6bb91ae6
Tx public key: b9994c46c784815c96055788716a08a71fe9475997b6eebc9d35ba0787749a66
Timestamp: 1729361819 Timestamp [UCT]: 2024-10-19 18:16:59 Age [y:d:h:m:s]: 00:211:01:37:19
Block: 1135158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150657 RingCT/type: yes/0
Extra: 01b9994c46c784815c96055788716a08a71fe9475997b6eebc9d35ba0787749a66021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d1eaa6ca6e278fb31c324b2a42e4e528d40974e5d6be4a1ef2f678eff14957f 0.600000000000 1618489 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": 1135168, "vin": [ { "gen": { "height": 1135158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d1eaa6ca6e278fb31c324b2a42e4e528d40974e5d6be4a1ef2f678eff14957f" } } ], "extra": [ 1, 185, 153, 76, 70, 199, 132, 129, 92, 150, 5, 87, 136, 113, 106, 8, 167, 31, 233, 71, 89, 151, 182, 238, 188, 157, 53, 186, 7, 135, 116, 154, 102, 2, 17, 0, 0, 0, 5, 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