Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad5c7f796ed03cef8d04f118c4ba1bfdb3ad0fababbcb40b06eee1e563dd35e

Tx prefix hash: f30ee01cc844c7a1ca845aeb810d1e6cceebdbe8a85244ea4ee46654783065f8
Tx public key: b2e6de7f2eb3104f7022d4ef9dceb0dbbf4e05777707f626c4167ecf1b112d67
Timestamp: 1675377782 Timestamp [UCT]: 2023-02-02 22:43:02 Age [y:d:h:m:s]: 02:023:08:59:50
Block: 688491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538292 RingCT/type: yes/0
Extra: 01b2e6de7f2eb3104f7022d4ef9dceb0dbbf4e05777707f626c4167ecf1b112d670211000000015029cbac000000000000000000

1 output(s) for total of 3.211762632000 dcy

stealth address amount amount idx
00: 1928e7341db1900ca0dccec7c1a0b273af373e2aba11aaa4016ad95fb83bd54d 3.211762632000 1131115 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": 688501, "vin": [ { "gen": { "height": 688491 } } ], "vout": [ { "amount": 3211762632, "target": { "key": "1928e7341db1900ca0dccec7c1a0b273af373e2aba11aaa4016ad95fb83bd54d" } } ], "extra": [ 1, 178, 230, 222, 127, 46, 179, 16, 79, 112, 34, 212, 239, 157, 206, 176, 219, 191, 78, 5, 119, 119, 7, 246, 38, 196, 22, 126, 207, 27, 17, 45, 103, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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