Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815d5f325f5d6684189c9164b5ddc6972afdc1573815f211e66925e13496e962

Tx prefix hash: 1f14b34bd73ae84fedc2cb9a0b88e630e0c849e7bcee5d77a455c965ee2e2003
Tx public key: 31f04203b23317063ec8c7cfb0acfa07c8b1f250cfc0c775c67be63fd3600f03
Timestamp: 1736488108 Timestamp [UCT]: 2025-01-10 05:48:28 Age [y:d:h:m:s]: 00:114:00:39:02
Block: 1194109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81294 RingCT/type: yes/0
Extra: 0131f04203b23317063ec8c7cfb0acfa07c8b1f250cfc0c775c67be63fd3600f030211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ea60126cf8a50845dedcd62e73666a4acc9a0e0d6c295ed827b7557219d73ae 0.600000000000 1680676 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": 1194119, "vin": [ { "gen": { "height": 1194109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ea60126cf8a50845dedcd62e73666a4acc9a0e0d6c295ed827b7557219d73ae" } } ], "extra": [ 1, 49, 240, 66, 3, 178, 51, 23, 6, 62, 200, 199, 207, 176, 172, 250, 7, 200, 177, 242, 80, 207, 192, 199, 117, 198, 123, 230, 63, 211, 96, 15, 3, 2, 17, 0, 0, 0, 6, 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