Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43505827764cf29a3435021793afa4e8448f85d8d0fca15cd90751b2872a0d1d

Tx prefix hash: 0382fa8db91fdeed7fa864d64741b00a80e8f6173af78be893e2768ecd0e36fa
Tx public key: cf9d92ae78ed472dc5ad3a0b547765cea69fcb284c1b8541fd91da349103cfa5
Timestamp: 1633624045 Timestamp [UCT]: 2021-10-07 16:27:25 Age [y:d:h:m:s]: 03:082:09:40:09
Block: 348532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836163 RingCT/type: yes/0
Extra: 01cf9d92ae78ed472dc5ad3a0b547765cea69fcb284c1b8541fd91da349103cfa502110000002df29d7abf000000000000000000

1 output(s) for total of 42.970383193000 dcy

stealth address amount amount idx
00: 65a95168e25713c1a73c2e06041c3a297f2de6f250dce8a6bf4dfb70efa9ee41 42.970383193000 713696 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": 348542, "vin": [ { "gen": { "height": 348532 } } ], "vout": [ { "amount": 42970383193, "target": { "key": "65a95168e25713c1a73c2e06041c3a297f2de6f250dce8a6bf4dfb70efa9ee41" } } ], "extra": [ 1, 207, 157, 146, 174, 120, 237, 71, 45, 197, 173, 58, 11, 84, 119, 101, 206, 166, 159, 203, 40, 76, 27, 133, 65, 253, 145, 218, 52, 145, 3, 207, 165, 2, 17, 0, 0, 0, 45, 242, 157, 122, 191, 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