Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7caa44b2b1916bb9e9f64bf952923415d84f3ca5bd0fa10f91527817fba8b6f9

Tx prefix hash: e0fd985e1b9eb6184e734670c1f26a0fa268fa466825eece7a1b84f9f9ee3102
Tx public key: ae5a6b9175561717fca0fb776da72e5a21fd768a360c3a74001d1f46d3282512
Timestamp: 1673127793 Timestamp [UCT]: 2023-01-07 21:43:13 Age [y:d:h:m:s]: 02:007:13:51:18
Block: 669826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527314 RingCT/type: yes/0
Extra: 01ae5a6b9175561717fca0fb776da72e5a21fd768a360c3a74001d1f46d328251202110000000152542ceb000000000000000000

1 output(s) for total of 3.703295449000 dcy

stealth address amount amount idx
00: f07750637062103e9d2495a9a5f5d5e860475fcdef7aa6a4a5fba1c2e4cbc259 3.703295449000 1111189 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": 669836, "vin": [ { "gen": { "height": 669826 } } ], "vout": [ { "amount": 3703295449, "target": { "key": "f07750637062103e9d2495a9a5f5d5e860475fcdef7aa6a4a5fba1c2e4cbc259" } } ], "extra": [ 1, 174, 90, 107, 145, 117, 86, 23, 23, 252, 160, 251, 119, 109, 167, 46, 90, 33, 253, 118, 138, 54, 12, 58, 116, 0, 29, 31, 70, 211, 40, 37, 18, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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