Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 048409909e53e799f2730fa10b9b10482f4516e16b2d77e3a243de7bc48e99bc

Tx prefix hash: b226144e4d8bd39c8210ebe67026c4b2fc2aa304e56aeaee8f91b778e46e5e5f
Tx public key: 64330a09b129a5e2beca207df7e51b504b4cfd2ae7165d0688dda1bcc338656f
Timestamp: 1708398309 Timestamp [UCT]: 2024-02-20 03:05:09 Age [y:d:h:m:s]: 01:090:14:03:51
Block: 961365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325807 RingCT/type: yes/0
Extra: 0164330a09b129a5e2beca207df7e51b504b4cfd2ae7165d0688dda1bcc338656f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166fe4604f0947e49911ecd6707e88fa355be902f5275655591d8b2a895c26a8 0.600000000000 1420974 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": 961375, "vin": [ { "gen": { "height": 961365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166fe4604f0947e49911ecd6707e88fa355be902f5275655591d8b2a895c26a8" } } ], "extra": [ 1, 100, 51, 10, 9, 177, 41, 165, 226, 190, 202, 32, 125, 247, 229, 27, 80, 75, 76, 253, 42, 231, 22, 93, 6, 136, 221, 161, 188, 195, 56, 101, 111, 2, 17, 0, 0, 0, 1, 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