Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a330fcc09ccae997f93357f18e0f402ec409f19cb4948e1f0e3e1398837155cc

Tx prefix hash: 57a45d2f0c084e5657305df7cdca9b52315ad345e158ddad31be232c395ddf48
Tx public key: 29a0a50580e86cbba5810b30ecc14a7a59d8b16ada0fe8dfc4fb1c5911b2d6f1
Timestamp: 1744511452 Timestamp [UCT]: 2025-04-13 02:30:52 Age [y:d:h:m:s]: 00:216:18:16:53
Block: 1260262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152645 RingCT/type: yes/0
Extra: 0129a0a50580e86cbba5810b30ecc14a7a59d8b16ada0fe8dfc4fb1c5911b2d6f10211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50dcceae978c827cea8785ffd6710996111a870e49a4405b77f8f0f1654b8167 0.600000000000 1747417 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": 1260272, "vin": [ { "gen": { "height": 1260262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50dcceae978c827cea8785ffd6710996111a870e49a4405b77f8f0f1654b8167" } } ], "extra": [ 1, 41, 160, 165, 5, 128, 232, 108, 187, 165, 129, 11, 48, 236, 193, 74, 122, 89, 216, 177, 106, 218, 15, 232, 223, 196, 251, 28, 89, 17, 178, 214, 241, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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