Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258a143fb6cf3a68adb4a8cc1633ba1f1be70170997f960a0c1ed6fbaa355387

Tx prefix hash: 84aa45616bd85c8101a4c06686ce09ab13eacb38fe89fd13cbcd31c0c949ce25
Tx public key: be48e8a73c74377d2d72424a7d34d87750266959bea1329235affa8b70e38d32
Timestamp: 1701685007 Timestamp [UCT]: 2023-12-04 10:16:47 Age [y:d:h:m:s]: 01:196:12:16:26
Block: 905708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401529 RingCT/type: yes/0
Extra: 01be48e8a73c74377d2d72424a7d34d87750266959bea1329235affa8b70e38d32021100000007faf35c9c000000000000000000

1 output(s) for total of 0.612369277000 dcy

stealth address amount amount idx
00: 2e4b1acd33f562ac67099b9273948a9d4e596a67d9e43f4c382603c95221bd63 0.612369277000 1362611 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": 905718, "vin": [ { "gen": { "height": 905708 } } ], "vout": [ { "amount": 612369277, "target": { "key": "2e4b1acd33f562ac67099b9273948a9d4e596a67d9e43f4c382603c95221bd63" } } ], "extra": [ 1, 190, 72, 232, 167, 60, 116, 55, 125, 45, 114, 66, 74, 125, 52, 216, 119, 80, 38, 105, 89, 190, 161, 50, 146, 53, 175, 250, 139, 112, 227, 141, 50, 2, 17, 0, 0, 0, 7, 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