Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 094b4a7f361d9402ae466d72f08c10bb70a1c14dfa13ee723b128bf5c2546c1c

Tx prefix hash: c487cd7cb2f2e86ae2707eec12b2752c69855b893b77908aedff1f9b73945e1b
Tx public key: 736d2b8ab207fae035cd500b529fc7ebffcbe2aa87405465b5a5515a15d94d4d
Timestamp: 1724679765 Timestamp [UCT]: 2024-08-26 13:42:45 Age [y:d:h:m:s]: 01:070:14:20:17
Block: 1096346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308898 RingCT/type: yes/0
Extra: 01736d2b8ab207fae035cd500b529fc7ebffcbe2aa87405465b5a5515a15d94d4d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a72b610901b10ba36180e8480936bf659cf8598e64d2154ec528b23531630bf 0.600000000000 1571535 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": 1096356, "vin": [ { "gen": { "height": 1096346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a72b610901b10ba36180e8480936bf659cf8598e64d2154ec528b23531630bf" } } ], "extra": [ 1, 115, 109, 43, 138, 178, 7, 250, 224, 53, 205, 80, 11, 82, 159, 199, 235, 255, 203, 226, 170, 135, 64, 84, 101, 181, 165, 81, 90, 21, 217, 77, 77, 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