Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d29c034b7e868662f87cc27a86303c4b5b3184ee3f036a6c8fed1c6967c253

Tx prefix hash: 5f9e00f76468b477d85ca3df57ada68f9af615700d89d89eec0b910206561e1e
Tx public key: b6bd158b5c50629b7785fc25baa99a2f6b0bb2915b6b28dcd28fa11297eb37c0
Timestamp: 1702900217 Timestamp [UCT]: 2023-12-18 11:50:17 Age [y:d:h:m:s]: 01:326:07:39:55
Block: 915787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492072 RingCT/type: yes/0
Extra: 01b6bd158b5c50629b7785fc25baa99a2f6b0bb2915b6b28dcd28fa11297eb37c0021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 486b50194f78f3d0160685d51bd550068762a99d7555eb92c825b3e67e77a802 0.600000000000 1373211 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": 915797, "vin": [ { "gen": { "height": 915787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "486b50194f78f3d0160685d51bd550068762a99d7555eb92c825b3e67e77a802" } } ], "extra": [ 1, 182, 189, 21, 139, 92, 80, 98, 155, 119, 133, 252, 37, 186, 169, 154, 47, 107, 11, 178, 145, 91, 107, 40, 220, 210, 143, 161, 18, 151, 235, 55, 192, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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