Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d148bf70dd7ee36d0d04c044e18ca32bc5918129fd4c624dec8a43fc18c9cf3

Tx prefix hash: 0ecb9470ddcd8a9bc47568db6556b45923641b80d3e783aa09614fa54c34e378
Tx public key: f4e355c0a53523e5eb9cbfc2d361456e1ac622f24b2eaafd3d7005e81a3bc475
Timestamp: 1704804254 Timestamp [UCT]: 2024-01-09 12:44:14 Age [y:d:h:m:s]: 01:025:13:33:13
Block: 931563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279330 RingCT/type: yes/0
Extra: 01f4e355c0a53523e5eb9cbfc2d361456e1ac622f24b2eaafd3d7005e81a3bc47502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9076ce22dcb2264d1cc4ae44a5b8024e77e81c2510ef0496649b4188e20d9ec4 0.600000000000 1389465 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": 931573, "vin": [ { "gen": { "height": 931563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9076ce22dcb2264d1cc4ae44a5b8024e77e81c2510ef0496649b4188e20d9ec4" } } ], "extra": [ 1, 244, 227, 85, 192, 165, 53, 35, 229, 235, 156, 191, 194, 211, 97, 69, 110, 26, 198, 34, 242, 75, 46, 170, 253, 61, 112, 5, 232, 26, 59, 196, 117, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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