Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e837f21304ce3855235685374af99f1a0d968eb3db77d0fb0a31ac0004717f0a

Tx prefix hash: aa5eb5790a54dc2bc1be0026597375b366fd59ff1844aeaf543c7bdf16af2a48
Tx public key: 040c4e7bd1ad265630be8aedf8fd4a27ea007f3c365e6dec0709c28a6e2a0d92
Timestamp: 1736055794 Timestamp [UCT]: 2025-01-05 05:43:14 Age [y:d:h:m:s]: 00:164:14:45:42
Block: 1190534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117350 RingCT/type: yes/0
Extra: 01040c4e7bd1ad265630be8aedf8fd4a27ea007f3c365e6dec0709c28a6e2a0d920211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 530049e4a036edf431e23c3880ecde3a7c2cc0980ffb3c3592239fe946bcac37 0.600000000000 1677051 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": 1190544, "vin": [ { "gen": { "height": 1190534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "530049e4a036edf431e23c3880ecde3a7c2cc0980ffb3c3592239fe946bcac37" } } ], "extra": [ 1, 4, 12, 78, 123, 209, 173, 38, 86, 48, 190, 138, 237, 248, 253, 74, 39, 234, 0, 127, 60, 54, 94, 109, 236, 7, 9, 194, 138, 110, 42, 13, 146, 2, 17, 0, 0, 0, 2, 31, 10, 83, 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