Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31300e510c28a7fc7d9eeef498cc5955b494c79607a05703723522e83e359691

Tx prefix hash: daf9a201becde8778e4948e5ef076cb1a2351202ab113c281419e9939a0e4f3e
Tx public key: 4aa75cf8ac3a4a4a7ae69aa62d0c8ad16a184b14de7932369c4132d88e5a30ad
Timestamp: 1675631919 Timestamp [UCT]: 2023-02-05 21:18:39 Age [y:d:h:m:s]: 02:092:08:41:45
Block: 690609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587642 RingCT/type: yes/0
Extra: 014aa75cf8ac3a4a4a7ae69aa62d0c8ad16a184b14de7932369c4132d88e5a30ad0211000000065029cbac000000000000000000

1 output(s) for total of 3.160280450000 dcy

stealth address amount amount idx
00: 1a6f52270706407701468ab52c119b4eaec667d2e2768f58a0794e33ccd79b1b 3.160280450000 1133339 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": 690619, "vin": [ { "gen": { "height": 690609 } } ], "vout": [ { "amount": 3160280450, "target": { "key": "1a6f52270706407701468ab52c119b4eaec667d2e2768f58a0794e33ccd79b1b" } } ], "extra": [ 1, 74, 167, 92, 248, 172, 58, 74, 74, 122, 230, 154, 166, 45, 12, 138, 209, 106, 24, 75, 20, 222, 121, 50, 54, 156, 65, 50, 216, 142, 90, 48, 173, 2, 17, 0, 0, 0, 6, 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