Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff85bb5e17290cafe6844b2a19ec3f4109ebea842c7ef536c7e930b79f88215e

Tx prefix hash: b0b7416347d019bb28fc6c711d0546a242f4356b67a88c6b5f580f7a7b5a3320
Tx public key: 7463b61e95a19176b5c28c501a255e54d707d0522627e856433f560be91a7cbb
Timestamp: 1751227830 Timestamp [UCT]: 2025-06-29 20:10:30 Age [y:d:h:m:s]: 00:133:01:54:45
Block: 1315385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93272 RingCT/type: yes/0
Extra: 017463b61e95a19176b5c28c501a255e54d707d0522627e856433f560be91a7cbb021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a6e10803ecac3e155311c34f1f157013e4c4180f52a9e990f22664f791f6af9 0.600000000000 1803040 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": 1315395, "vin": [ { "gen": { "height": 1315385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a6e10803ecac3e155311c34f1f157013e4c4180f52a9e990f22664f791f6af9" } } ], "extra": [ 1, 116, 99, 182, 30, 149, 161, 145, 118, 181, 194, 140, 80, 26, 37, 94, 84, 215, 7, 208, 82, 38, 39, 232, 86, 67, 63, 86, 11, 233, 26, 124, 187, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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