Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810104d931193be45bf4d1fb16283919f5526c5cd42dfe13d415417de55a59ff

Tx prefix hash: 686f5016bb4b029ee1bdce008359143706317a176870b79207446296cd1c45b6
Tx public key: 015f775d70a793952c819f054314daf612a0f8a05a01b5f9a39020223d1ec6e9
Timestamp: 1686298119 Timestamp [UCT]: 2023-06-09 08:08:39 Age [y:d:h:m:s]: 01:159:17:19:24
Block: 778406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375509 RingCT/type: yes/0
Extra: 01015f775d70a793952c819f054314daf612a0f8a05a01b5f9a39020223d1ec6e9021100000004faf35c9c000000000000000000

1 output(s) for total of 1.617401911000 dcy

stealth address amount amount idx
00: 374b2d1c76d3198efa4bc317e2a1b6606809e6964a3583b754e6a365a8d31e40 1.617401911000 1228029 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": 778416, "vin": [ { "gen": { "height": 778406 } } ], "vout": [ { "amount": 1617401911, "target": { "key": "374b2d1c76d3198efa4bc317e2a1b6606809e6964a3583b754e6a365a8d31e40" } } ], "extra": [ 1, 1, 95, 119, 93, 112, 167, 147, 149, 44, 129, 159, 5, 67, 20, 218, 246, 18, 160, 248, 160, 90, 1, 181, 249, 163, 144, 32, 34, 61, 30, 198, 233, 2, 17, 0, 0, 0, 4, 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