Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcf4e2f90f8f7ee8d0a24242cf5a357748f89564873c4b4f12259a772ca3905d

Tx prefix hash: ea095eef45c9ddf697455dcbb3983c5b1c04fef57575cacbef11fc1fbc9d892c
Tx public key: 041cefa8e81030c36b71c952d3ac8d2fa2bc0707269882501592df1d4af372fb
Timestamp: 1752608899 Timestamp [UCT]: 2025-07-15 19:48:19 Age [y:d:h:m:s]: 00:128:18:48:16
Block: 1326235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90773 RingCT/type: yes/0
Extra: 01041cefa8e81030c36b71c952d3ac8d2fa2bc0707269882501592df1d4af372fb021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be2588743ae197a1a283361a21a19cca65b53e362271d2613ea369a894b41ce4 0.600000000000 1813986 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": 1326245, "vin": [ { "gen": { "height": 1326235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be2588743ae197a1a283361a21a19cca65b53e362271d2613ea369a894b41ce4" } } ], "extra": [ 1, 4, 28, 239, 168, 232, 16, 48, 195, 107, 113, 201, 82, 211, 172, 141, 47, 162, 188, 7, 7, 38, 152, 130, 80, 21, 146, 223, 29, 74, 243, 114, 251, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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