Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479cf85ecaaa489a14ee025f08c2c9a99ce5ae62c7f78c6d1793d97b81bfa8ff

Tx prefix hash: 7b9ffdc1c6a7caabbcebea03f0e77b5c1a179a10c75e74ed816f52d56882712a
Tx public key: db4391a57b8d11facbda0c508368c5c6fb830d7d6b37eda40a3c3eea5041d8f0
Timestamp: 1759251124 Timestamp [UCT]: 2025-09-30 16:52:04 Age [y:d:h:m:s]: 00:041:11:51:50
Block: 1379845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29714 RingCT/type: yes/0
Extra: 01db4391a57b8d11facbda0c508368c5c6fb830d7d6b37eda40a3c3eea5041d8f002110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea4c7a47d4e2f3b136a7be411dfca5c7b539bec499f215ada63e50fcb9e8bc8d 0.600000000000 1867954 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": 1379855, "vin": [ { "gen": { "height": 1379845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea4c7a47d4e2f3b136a7be411dfca5c7b539bec499f215ada63e50fcb9e8bc8d" } } ], "extra": [ 1, 219, 67, 145, 165, 123, 141, 17, 250, 203, 218, 12, 80, 131, 104, 197, 198, 251, 131, 13, 125, 107, 55, 237, 164, 10, 60, 62, 234, 80, 65, 216, 240, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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