Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b849e5a702c3727d53d8e73cecfdbcef2e4377a87c59f92bc9e27cbe71e44b07

Tx prefix hash: fcda7c155c74083f59e0a5fb74f5d38f7ecb8ff0fa1db2f90e5d95c3f80485c1
Tx public key: c1086523021cbeb10335675cae2a3914648c55060731626aabefe3cbdc41e931
Timestamp: 1724894815 Timestamp [UCT]: 2024-08-29 01:26:55 Age [y:d:h:m:s]: 00:241:20:22:09
Block: 1098134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172727 RingCT/type: yes/0
Extra: 01c1086523021cbeb10335675cae2a3914648c55060731626aabefe3cbdc41e93102110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f13e4c99f31281e9bac25033d65b0975d594a1d8a24b98b0ecd7c8f5c069ef8 0.600000000000 1573745 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": 1098144, "vin": [ { "gen": { "height": 1098134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f13e4c99f31281e9bac25033d65b0975d594a1d8a24b98b0ecd7c8f5c069ef8" } } ], "extra": [ 1, 193, 8, 101, 35, 2, 28, 190, 177, 3, 53, 103, 92, 174, 42, 57, 20, 100, 140, 85, 6, 7, 49, 98, 106, 171, 239, 227, 203, 220, 65, 233, 49, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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