Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06570e30a673d41d5817507730e72b352c5b0af1d585496e4d6cbcc36acffff1

Tx prefix hash: b34dcb69a36cd84d3be2b1c6923ff13e7a8ab18ee294be9a2488e84533bf1243
Tx public key: 498c0a292889ff8fd11488131bf74a197b4785c4bc12661315f51abd52c8474d
Timestamp: 1719278860 Timestamp [UCT]: 2024-06-25 01:27:40 Age [y:d:h:m:s]: 00:322:13:42:35
Block: 1051565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230534 RingCT/type: yes/0
Extra: 01498c0a292889ff8fd11488131bf74a197b4785c4bc12661315f51abd52c8474d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 611114e971d6e816f2bd8a3d951a60d44fc8d97666aa466ba30601a47d143e54 0.600000000000 1521878 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": 1051575, "vin": [ { "gen": { "height": 1051565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "611114e971d6e816f2bd8a3d951a60d44fc8d97666aa466ba30601a47d143e54" } } ], "extra": [ 1, 73, 140, 10, 41, 40, 137, 255, 143, 209, 20, 136, 19, 27, 247, 74, 25, 123, 71, 133, 196, 188, 18, 102, 19, 21, 245, 26, 189, 82, 200, 71, 77, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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