Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edc13783fb9373ce54780dcefc4d70c89f3dedc4c03521c02275fded8f7cfe7e

Tx prefix hash: 9cf13f17eb41e370f31e62948dcf0cb5ede7a0023795c57b7357245bc7ee0c7e
Tx public key: 62cc4de17575fbfe6f5ea448c270a1ca809d177125fa8b7cbef45af6e5ed8125
Timestamp: 1728396447 Timestamp [UCT]: 2024-10-08 14:07:27 Age [y:d:h:m:s]: 00:173:21:07:10
Block: 1127164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124064 RingCT/type: yes/0
Extra: 0162cc4de17575fbfe6f5ea448c270a1ca809d177125fa8b7cbef45af6e5ed8125021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75c5ceeab08b904e808d17e0fe50b349da4ddcf34d7cb7a6a00c683fdb30900 0.600000000000 1609963 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": 1127174, "vin": [ { "gen": { "height": 1127164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75c5ceeab08b904e808d17e0fe50b349da4ddcf34d7cb7a6a00c683fdb30900" } } ], "extra": [ 1, 98, 204, 77, 225, 117, 117, 251, 254, 111, 94, 164, 72, 194, 112, 161, 202, 128, 157, 23, 113, 37, 250, 139, 124, 190, 244, 90, 246, 229, 237, 129, 37, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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