Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc6e049d6c3ddf9abf71018ee4df4c2a804767457f1805e580a62031f6f64b0b

Tx prefix hash: b49528caa913d5457293bee6fe1042702ddffe3540bed70d76104f3a0870734d
Tx public key: 3ee887135414b7e020d45aefaf0a542b46d30aae98512076e5a7a7aa6545a03a
Timestamp: 1735733121 Timestamp [UCT]: 2025-01-01 12:05:21 Age [y:d:h:m:s]: 00:169:22:59:53
Block: 1187859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121145 RingCT/type: yes/0
Extra: 013ee887135414b7e020d45aefaf0a542b46d30aae98512076e5a7a7aa6545a03a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b678aa98c45d52079c1ea0fd019385f1eaf6d7944e2d34aa3f12d0841174017 0.600000000000 1674356 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": 1187869, "vin": [ { "gen": { "height": 1187859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b678aa98c45d52079c1ea0fd019385f1eaf6d7944e2d34aa3f12d0841174017" } } ], "extra": [ 1, 62, 232, 135, 19, 84, 20, 183, 224, 32, 212, 90, 239, 175, 10, 84, 43, 70, 211, 10, 174, 152, 81, 32, 118, 229, 167, 167, 170, 101, 69, 160, 58, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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