Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b253476bfed7c9fccba8f93ad32af5e42fb7eb2b5414cefef29b068f347999

Tx prefix hash: aac7e17faaa3b32f6ae643a2a1f22c7d1c99b078d0eb77b647587eed4ca0e494
Tx public key: 1c9e0914aab0b232ed96742ce7f897a989c7bfd9ee5d3a41a69b3806f46a59b9
Timestamp: 1639053009 Timestamp [UCT]: 2021-12-09 12:30:09 Age [y:d:h:m:s]: 03:327:04:44:47
Block: 391764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1010311 RingCT/type: yes/0
Extra: 011c9e0914aab0b232ed96742ce7f897a989c7bfd9ee5d3a41a69b3806f46a59b9021100000019379224c2000000000000000000

1 output(s) for total of 30.897518612000 dcy

stealth address amount amount idx
00: 2f077e5a7dd1226f2db1df69f9035a7c290eaaed0761d45cfa46c72140ebd5d4 30.897518612000 788329 of 0

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": 391774, "vin": [ { "gen": { "height": 391764 } } ], "vout": [ { "amount": 30897518612, "target": { "key": "2f077e5a7dd1226f2db1df69f9035a7c290eaaed0761d45cfa46c72140ebd5d4" } } ], "extra": [ 1, 28, 158, 9, 20, 170, 176, 178, 50, 237, 150, 116, 44, 231, 248, 151, 169, 137, 199, 191, 217, 238, 93, 58, 65, 166, 155, 56, 6, 244, 106, 89, 185, 2, 17, 0, 0, 0, 25, 55, 146, 36, 194, 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