Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aceb49a48f8e5724e01f5c1e687796b7bba2d0a84d1da501062d86247e3c6d71

Tx prefix hash: d2f7d9b2fd0ade66734d38b4b34b682f13c568dc711d71d2add1bd6eea6b5b1f
Tx public key: d8ae0682ce8517b86b638cc249ef255f356ff083e8d83c298149493343652b6e
Timestamp: 1764298476 Timestamp [UCT]: 2025-11-28 02:54:36 Age [y:d:h:m:s]: 00:025:19:49:57
Block: 1421684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18478 RingCT/type: yes/0
Extra: 01d8ae0682ce8517b86b638cc249ef255f356ff083e8d83c298149493343652b6e02110000000a4e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 180f15d019ed5e9bbec7bf7ea71b53132ebe3f5fb330dc037f135957abe3abbe 0.600000000000 1910241 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": 1421694, "vin": [ { "gen": { "height": 1421684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "180f15d019ed5e9bbec7bf7ea71b53132ebe3f5fb330dc037f135957abe3abbe" } } ], "extra": [ 1, 216, 174, 6, 130, 206, 133, 23, 184, 107, 99, 140, 194, 73, 239, 37, 95, 53, 111, 240, 131, 232, 216, 60, 41, 129, 73, 73, 51, 67, 101, 43, 110, 2, 17, 0, 0, 0, 10, 78, 123, 252, 9, 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