Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04514cf576410f6ba22127fc0f2c824e4fae5af756874d20f5fbd9715b5046e9

Tx prefix hash: 767a90fb5e7a6f5ac71b6f7b4c91ac95129006a4cbaf2a7da14c25a34a9f3233
Tx public key: 58594562aa9b405e0efabca5342841d0b963bbaf90b2b2a29d2038469ab0b655
Timestamp: 1718516348 Timestamp [UCT]: 2024-06-16 05:39:08 Age [y:d:h:m:s]: 00:129:12:51:08
Block: 1045272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92737 RingCT/type: yes/0
Extra: 0158594562aa9b405e0efabca5342841d0b963bbaf90b2b2a29d2038469ab0b655021100000001f0f115fa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80d4ca043260632ae870a753edd57e78f22fc4f5a157cd97485324b38fdbc052 0.600000000000 1514797 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": 1045282, "vin": [ { "gen": { "height": 1045272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80d4ca043260632ae870a753edd57e78f22fc4f5a157cd97485324b38fdbc052" } } ], "extra": [ 1, 88, 89, 69, 98, 170, 155, 64, 94, 14, 250, 188, 165, 52, 40, 65, 208, 185, 99, 187, 175, 144, 178, 178, 162, 157, 32, 56, 70, 154, 176, 182, 85, 2, 17, 0, 0, 0, 1, 240, 241, 21, 250, 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