Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26a165d2ef4e3998b74a770bc0ebea4ef0d87233e4841d5a18880d8b73dc8f5

Tx prefix hash: 6a81a00fcb06899f4322d3322e624af3365b2bdb2a2e74c66476328d621ba857
Tx public key: 4d7f2d561786653b6deade51f3c20b72c8e59a3e49fc7134e8a27da41ed53bcc
Timestamp: 1709849574 Timestamp [UCT]: 2024-03-07 22:12:54 Age [y:d:h:m:s]: 01:300:20:30:10
Block: 973413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473804 RingCT/type: yes/0
Extra: 014d7f2d561786653b6deade51f3c20b72c8e59a3e49fc7134e8a27da41ed53bcc02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de77e91ddc3cda4abc30ea487de7b9208dabb141e7d78c54822126eb0a78ba59 0.600000000000 1433348 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": 973423, "vin": [ { "gen": { "height": 973413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de77e91ddc3cda4abc30ea487de7b9208dabb141e7d78c54822126eb0a78ba59" } } ], "extra": [ 1, 77, 127, 45, 86, 23, 134, 101, 59, 109, 234, 222, 81, 243, 194, 11, 114, 200, 229, 154, 62, 73, 252, 113, 52, 232, 162, 125, 164, 30, 213, 59, 204, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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