Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b056b81e1664a08d8d3326dd58661bf5878e35d05f7e47c0b66e2be6937efc2

Tx prefix hash: d090e88d25a21b05f7230b9008c53418842501e0f32faf144b576893651e8192
Tx public key: c691e7d8402c2ea01c70f5ab543d6dadd82b639b651e02aae85000ea2e5bcab4
Timestamp: 1707292136 Timestamp [UCT]: 2024-02-07 07:48:56 Age [y:d:h:m:s]: 01:054:06:13:03
Block: 952188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299828 RingCT/type: yes/0
Extra: 01c691e7d8402c2ea01c70f5ab543d6dadd82b639b651e02aae85000ea2e5bcab4021100000001ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff208795d69ba2be083a4c9e2e922f0222e30ddf86be766451d2a959c1ca13be 0.600000000000 1411072 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": 952198, "vin": [ { "gen": { "height": 952188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff208795d69ba2be083a4c9e2e922f0222e30ddf86be766451d2a959c1ca13be" } } ], "extra": [ 1, 198, 145, 231, 216, 64, 44, 46, 160, 28, 112, 245, 171, 84, 61, 109, 173, 216, 43, 99, 155, 101, 30, 2, 170, 232, 80, 0, 234, 46, 91, 202, 180, 2, 17, 0, 0, 0, 1, 236, 87, 178, 52, 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