Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020670a8e24702de021c86bd99d0a9df9d3404ca2d4d99f94fa0d0a3942908be

Tx prefix hash: 4c0bb973992c543f5c5a39326dce987c7949a77c2c0f78f5bad9f7765227bc87
Tx public key: 8298aee45ef6c54f5460a08c2b612b4a2e44b4531db67fe79e649b996066e078
Timestamp: 1706747347 Timestamp [UCT]: 2024-02-01 00:29:07 Age [y:d:h:m:s]: 01:064:11:44:35
Block: 947661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307180 RingCT/type: yes/0
Extra: 018298aee45ef6c54f5460a08c2b612b4a2e44b4531db67fe79e649b996066e07802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c3a4819c452cf97f3262491ece97a1353bf83745b1a64c642b5c0d6de466d08 0.600000000000 1406019 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": 947671, "vin": [ { "gen": { "height": 947661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c3a4819c452cf97f3262491ece97a1353bf83745b1a64c642b5c0d6de466d08" } } ], "extra": [ 1, 130, 152, 174, 228, 94, 246, 197, 79, 84, 96, 160, 140, 43, 97, 43, 74, 46, 68, 180, 83, 29, 182, 127, 231, 158, 100, 155, 153, 96, 102, 224, 120, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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