Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3785381b7beacf7dd9d69f1f94f779817821b42bb19804a6290f1c57c54c8048

Tx prefix hash: 9003e0f14031e5a42417564d7bbca604dd9870e0164a6931a8d206af2f982ded
Tx public key: 0b2ab2a45f321d5fe05413c9442c13eb40770965a7fbe80f0cd842f4db199d12
Timestamp: 1674047012 Timestamp [UCT]: 2023-01-18 13:03:32 Age [y:d:h:m:s]: 02:143:15:25:01
Block: 677444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624389 RingCT/type: yes/0
Extra: 010b2ab2a45f321d5fe05413c9442c13eb40770965a7fbe80f0cd842f4db199d12021100000003e6d27f9c000000000000000000

1 output(s) for total of 3.494191911000 dcy

stealth address amount amount idx
00: eed993f7b214bfe8344c2622430cf9a67f7e36489fd2b21ba6d9f45bd12cc1a1 3.494191911000 1119219 of 0

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": 677454, "vin": [ { "gen": { "height": 677444 } } ], "vout": [ { "amount": 3494191911, "target": { "key": "eed993f7b214bfe8344c2622430cf9a67f7e36489fd2b21ba6d9f45bd12cc1a1" } } ], "extra": [ 1, 11, 42, 178, 164, 95, 50, 29, 95, 224, 84, 19, 201, 68, 44, 19, 235, 64, 119, 9, 101, 167, 251, 232, 15, 12, 216, 66, 244, 219, 25, 157, 18, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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