Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27a5b387e558023fc98a67b2db13173e71a8689815b0e309aac2d7a325c3e134

Tx prefix hash: db84603a812e8a9f1660264f58ce7d0f18277e41f9559340df342286ef02b545
Tx public key: 1b5f2a506c0b992ee71a7392ea3815cdd944d4be324794354c66878c4304cd42
Timestamp: 1736817433 Timestamp [UCT]: 2025-01-14 01:17:13 Age [y:d:h:m:s]: 00:155:08:08:34
Block: 1196835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110733 RingCT/type: yes/0
Extra: 011b5f2a506c0b992ee71a7392ea3815cdd944d4be324794354c66878c4304cd420211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73795517a8eae8d8856679b6b3019f532f5fe82c15eadc77c514301417ded29d 0.600000000000 1683438 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": 1196845, "vin": [ { "gen": { "height": 1196835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73795517a8eae8d8856679b6b3019f532f5fe82c15eadc77c514301417ded29d" } } ], "extra": [ 1, 27, 95, 42, 80, 108, 11, 153, 46, 231, 26, 115, 146, 234, 56, 21, 205, 217, 68, 212, 190, 50, 71, 148, 53, 76, 102, 135, 140, 67, 4, 205, 66, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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