Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cefd3206ec48a19abcc177085469dc2bb78359737fbdb134b7c9a953e95c3d

Tx prefix hash: a0424d662025c17c0511bc4956e0d926c42295d12b6c7c134795a9d4b5c9a187
Tx public key: d5d1a42f2986d458448a981eeafaaf04282b101217452bf40569b0a1474a163e
Timestamp: 1661507291 Timestamp [UCT]: 2022-08-26 09:48:11 Age [y:d:h:m:s]: 02:142:13:11:55
Block: 574144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623340 RingCT/type: yes/0
Extra: 01d5d1a42f2986d458448a981eeafaaf04282b101217452bf40569b0a1474a163e021100000004e6d27f9c000000000000000000

1 output(s) for total of 7.684625125000 dcy

stealth address amount amount idx
00: b3b478f6403847d9b8e84ae1f29710e36d47371d81e1cc952c07d86d7cbbdbb3 7.684625125000 1007452 of 0

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": 574154, "vin": [ { "gen": { "height": 574144 } } ], "vout": [ { "amount": 7684625125, "target": { "key": "b3b478f6403847d9b8e84ae1f29710e36d47371d81e1cc952c07d86d7cbbdbb3" } } ], "extra": [ 1, 213, 209, 164, 47, 41, 134, 212, 88, 68, 138, 152, 30, 234, 250, 175, 4, 40, 43, 16, 18, 23, 69, 43, 244, 5, 105, 176, 161, 71, 74, 22, 62, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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