Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4eea52c89c150520073f8d81b3f198c4f297414a481f7be24d1463005b279a1

Tx prefix hash: 072646b7d2c4a39931d3c9ed527c8cccb29239f05edd61fff2f8398b78a6ff35
Tx public key: 2c4cb3cc38f246b5a922c2baf95c5f246cd55594691b48a6830e792c96b6b597
Timestamp: 1727969877 Timestamp [UCT]: 2024-10-03 15:37:57 Age [y:d:h:m:s]: 00:211:00:09:57
Block: 1123635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150612 RingCT/type: yes/0
Extra: 012c4cb3cc38f246b5a922c2baf95c5f246cd55594691b48a6830e792c96b6b597021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f13040c299143f21ed392f6b1bcee90e30a8328f745cbaa1b8d35afdf89afcd6 0.600000000000 1606170 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": 1123645, "vin": [ { "gen": { "height": 1123635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13040c299143f21ed392f6b1bcee90e30a8328f745cbaa1b8d35afdf89afcd6" } } ], "extra": [ 1, 44, 76, 179, 204, 56, 242, 70, 181, 169, 34, 194, 186, 249, 92, 95, 36, 108, 213, 85, 148, 105, 27, 72, 166, 131, 14, 121, 44, 150, 182, 181, 151, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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