Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b857b86dd330cae926ee5a4f4e9edac931630465959853b505a2de31e275927a

Tx prefix hash: 259c425a9fc07207d3f556537defc4eea03180e8c095fb90094decc1204db1a1
Tx public key: c3d31c1783d4142bc2b8b00f5e2f27da9c7b8e914198e0f3eee81b8c8b5fc53c
Timestamp: 1705946296 Timestamp [UCT]: 2024-01-22 17:58:16 Age [y:d:h:m:s]: 01:034:03:19:02
Block: 941008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285469 RingCT/type: yes/0
Extra: 01c3d31c1783d4142bc2b8b00f5e2f27da9c7b8e914198e0f3eee81b8c8b5fc53c02110000001859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfdad83c77d8d189d334927af56028fceea9ed611a7483cdd76e223b825ab940 0.600000000000 1399150 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": 941018, "vin": [ { "gen": { "height": 941008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfdad83c77d8d189d334927af56028fceea9ed611a7483cdd76e223b825ab940" } } ], "extra": [ 1, 195, 211, 28, 23, 131, 212, 20, 43, 194, 184, 176, 15, 94, 47, 39, 218, 156, 123, 142, 145, 65, 152, 224, 243, 238, 232, 27, 140, 139, 95, 197, 60, 2, 17, 0, 0, 0, 24, 89, 218, 211, 245, 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