Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e15cb05f7f409c9ae0f1b3b810c5a1d0d66562684b6d820e2c9ef8eee4462ef

Tx prefix hash: d23c74a017495704c1a148d605db9efbd680df1697308a568d9fd6e47e1be6d3
Tx public key: c4b4aa35ede8b8af6b3ea7f117cb0b60fe7a799ebb9e4cce1515c98e263de8a7
Timestamp: 1741805754 Timestamp [UCT]: 2025-03-12 18:55:54 Age [y:d:h:m:s]: 00:299:04:49:08
Block: 1237875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211658 RingCT/type: yes/0
Extra: 01c4b4aa35ede8b8af6b3ea7f117cb0b60fe7a799ebb9e4cce1515c98e263de8a7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad3ad15c56f858c0c99e8359044e9df3aca3739335a5219971bbfa4548f0e393 0.600000000000 1724834 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": 1237885, "vin": [ { "gen": { "height": 1237875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad3ad15c56f858c0c99e8359044e9df3aca3739335a5219971bbfa4548f0e393" } } ], "extra": [ 1, 196, 180, 170, 53, 237, 232, 184, 175, 107, 62, 167, 241, 23, 203, 11, 96, 254, 122, 121, 158, 187, 158, 76, 206, 21, 21, 201, 142, 38, 61, 232, 167, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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