Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c6918cf59ac9b4f33dc8ee39d5d52046a3fc05ed6421128fbfb4483c6bf61d9

Tx prefix hash: 17b5752c46b720735431d281b3f2b243849654123c33fdd1cb20d2039a2ea7d6
Tx public key: 8a6693965aeb2ee3221023a9c2c3caa06437ba99fde51e707eaf1f01d64ac540
Timestamp: 1718445040 Timestamp [UCT]: 2024-06-15 09:50:40 Age [y:d:h:m:s]: 00:212:00:39:20
Block: 1044676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151722 RingCT/type: yes/0
Extra: 018a6693965aeb2ee3221023a9c2c3caa06437ba99fde51e707eaf1f01d64ac5400211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50a9eec6dc7b7c5e19db53d2aa606d6b18a4d1e87efae033e2dff595758cfd70 0.600000000000 1514047 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": 1044686, "vin": [ { "gen": { "height": 1044676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50a9eec6dc7b7c5e19db53d2aa606d6b18a4d1e87efae033e2dff595758cfd70" } } ], "extra": [ 1, 138, 102, 147, 150, 90, 235, 46, 227, 34, 16, 35, 169, 194, 195, 202, 160, 100, 55, 186, 153, 253, 229, 30, 112, 126, 175, 31, 1, 214, 74, 197, 64, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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