Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4552a75f73d27f7e0a5a3f39d1ebd20b7736f2e98201d9a9a495e9d29d1ad512

Tx prefix hash: 12e48f75251f8373b48041f02661c098dea16585fac972d4e6193cb4ddc374d7
Tx public key: 499bfce7bee884f8ca96ea5cdce98aab3b492688a5f1f3603df629d29b54f150
Timestamp: 1725791389 Timestamp [UCT]: 2024-09-08 10:29:49 Age [y:d:h:m:s]: 00:248:18:31:25
Block: 1105571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177661 RingCT/type: yes/0
Extra: 01499bfce7bee884f8ca96ea5cdce98aab3b492688a5f1f3603df629d29b54f15002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10abda65a7badd0f3070cfd0dfa60730cfd3e8cb93b8ca7f2ec28499e0f52452 0.600000000000 1582946 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": 1105581, "vin": [ { "gen": { "height": 1105571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10abda65a7badd0f3070cfd0dfa60730cfd3e8cb93b8ca7f2ec28499e0f52452" } } ], "extra": [ 1, 73, 155, 252, 231, 190, 232, 132, 248, 202, 150, 234, 92, 220, 233, 138, 171, 59, 73, 38, 136, 165, 241, 243, 96, 61, 246, 41, 210, 155, 84, 241, 80, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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