Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4459faa116832c5a242ec679ab39fcbb3d1200003df238f3f356e8546d30f3bf

Tx prefix hash: 60e3eeb1dd0d1586c286717ecb28d37f61fea586ef8bb249a2b1c1f0b23ea806
Tx public key: 317f980ad40cbcc0ef76e5c01b2e0e91979395ccb5a4c04f61dd2b46372b680f
Timestamp: 1747272520 Timestamp [UCT]: 2025-05-15 01:28:40 Age [y:d:h:m:s]: 00:146:03:28:37
Block: 1283125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102092 RingCT/type: yes/0
Extra: 01317f980ad40cbcc0ef76e5c01b2e0e91979395ccb5a4c04f61dd2b46372b680f0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1eee3d0456e29587bb1ebaaed1d174331e4259a7c9e842929f0ee59ce22f241 0.600000000000 1770542 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": 1283135, "vin": [ { "gen": { "height": 1283125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1eee3d0456e29587bb1ebaaed1d174331e4259a7c9e842929f0ee59ce22f241" } } ], "extra": [ 1, 49, 127, 152, 10, 212, 12, 188, 192, 239, 118, 229, 192, 27, 46, 14, 145, 151, 147, 149, 204, 181, 164, 192, 79, 97, 221, 43, 70, 55, 43, 104, 15, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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