Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1e8ff95033480a2e7a7a1e9c37f79c6de12ee0e06c1ca282b994603bed7274

Tx prefix hash: f6a59520b42195c2c33f23f615a8344fbbbec87207f523e5e9137221f2281183
Tx public key: 2608c4fddc68ddae30a5f1541aa356b1ae9bee447439f5f4909894c8fbcd3840
Timestamp: 1725911490 Timestamp [UCT]: 2024-09-09 19:51:30 Age [y:d:h:m:s]: 01:070:05:50:27
Block: 1106577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308626 RingCT/type: yes/0
Extra: 012608c4fddc68ddae30a5f1541aa356b1ae9bee447439f5f4909894c8fbcd3840021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3bd73e3e822ba230d3d85100db326caaed7bc7521bfbb64eb98320e6978619b 0.600000000000 1584178 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": 1106587, "vin": [ { "gen": { "height": 1106577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3bd73e3e822ba230d3d85100db326caaed7bc7521bfbb64eb98320e6978619b" } } ], "extra": [ 1, 38, 8, 196, 253, 220, 104, 221, 174, 48, 165, 241, 84, 26, 163, 86, 177, 174, 155, 238, 68, 116, 57, 245, 244, 144, 152, 148, 200, 251, 205, 56, 64, 2, 17, 0, 0, 0, 3, 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