Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 621ca3220056d0b839218883e78aef1e5dcc269b6c26aad15cceebfbce20d7a5

Tx prefix hash: 78e27e16d324e85b0ee9d524eef9bb0f4272c27673de825e41f05835a566ce3c
Tx public key: df309a775bf85339f5d2e04b0baf2d06f5e7ccfba84b93f4160aed8e675fed7a
Timestamp: 1758774426 Timestamp [UCT]: 2025-09-25 04:27:06 Age [y:d:h:m:s]: 00:127:23:49:27
Block: 1375902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91466 RingCT/type: yes/0
Extra: 01df309a775bf85339f5d2e04b0baf2d06f5e7ccfba84b93f4160aed8e675fed7a021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 273afec79c402420fa29001d3e2d7919cadcad5a0c8c36733f4ce8036c338175 0.600000000000 1863993 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": 1375912, "vin": [ { "gen": { "height": 1375902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "273afec79c402420fa29001d3e2d7919cadcad5a0c8c36733f4ce8036c338175" } } ], "extra": [ 1, 223, 48, 154, 119, 91, 248, 83, 57, 245, 210, 224, 75, 11, 175, 45, 6, 245, 231, 204, 251, 168, 75, 147, 244, 22, 10, 237, 142, 103, 95, 237, 122, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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