Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4e362c355a164c642263cc04cdddbf1c0c5ffa58a3ecacb5de82b1e8352cf8c

Tx prefix hash: 9c307fb12aadf6b878049a2a833c480a90cb93583c52fc785e99c26904988c6c
Tx public key: 9506e7ed2785cf944062e9c63c87dca5d12d5609ba93e0442576c00d1c875982
Timestamp: 1699770891 Timestamp [UCT]: 2023-11-12 06:34:51 Age [y:d:h:m:s]: 01:153:21:02:44
Block: 889857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371171 RingCT/type: yes/0
Extra: 019506e7ed2785cf944062e9c63c87dca5d12d5609ba93e0442576c00d1c87598202110000000274c3735f000000000000000000

1 output(s) for total of 0.691089604000 dcy

stealth address amount amount idx
00: 45944960991b991bc05baa29aa1ce4eae3007c3e07ad349c1f8051b5ff7500e4 0.691089604000 1345874 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": 889867, "vin": [ { "gen": { "height": 889857 } } ], "vout": [ { "amount": 691089604, "target": { "key": "45944960991b991bc05baa29aa1ce4eae3007c3e07ad349c1f8051b5ff7500e4" } } ], "extra": [ 1, 149, 6, 231, 237, 39, 133, 207, 148, 64, 98, 233, 198, 60, 135, 220, 165, 209, 45, 86, 9, 186, 147, 224, 68, 37, 118, 192, 13, 28, 135, 89, 130, 2, 17, 0, 0, 0, 2, 116, 195, 115, 95, 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