Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74622fe18dc593e70ec856cd4a5ec71877f17eb64ce7b73f2850d2b0f2e85896

Tx prefix hash: 3b6372a323eae6120575ff6d9e0fe7ca571c58f63dd7d7616f281bfa536a8764
Tx public key: 9c866e921e8a0a6c9d84da1a4c52f1ed7c6316f223d1d959c1a7ee3380e82d19
Timestamp: 1731833313 Timestamp [UCT]: 2024-11-17 08:48:33 Age [y:d:h:m:s]: 01:029:20:49:28
Block: 1155559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279804 RingCT/type: yes/0
Extra: 019c866e921e8a0a6c9d84da1a4c52f1ed7c6316f223d1d959c1a7ee3380e82d19021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 885f711845eb197a1818fa6181266052fdd8df47c2744134262d16bda99d0c44 0.600000000000 1641176 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": 1155569, "vin": [ { "gen": { "height": 1155559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "885f711845eb197a1818fa6181266052fdd8df47c2744134262d16bda99d0c44" } } ], "extra": [ 1, 156, 134, 110, 146, 30, 138, 10, 108, 157, 132, 218, 26, 76, 82, 241, 237, 124, 99, 22, 242, 35, 209, 217, 89, 193, 167, 238, 51, 128, 232, 45, 25, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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