Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ba1f07621ac023347c1545779c6d7fb3323c8442d271229fb36601ba372a21

Tx prefix hash: 92b0f94e85457fb6a5e8f0b92e7adb9fe68aa8442c1974fa84a2516e0cb75310
Tx public key: 28997f9ed84c85064d20a57057400eb6904fdde056c70a3caf3e5f3ed159a4d8
Timestamp: 1728458805 Timestamp [UCT]: 2024-10-09 07:26:45 Age [y:d:h:m:s]: 00:106:13:31:41
Block: 1127678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76133 RingCT/type: yes/0
Extra: 0128997f9ed84c85064d20a57057400eb6904fdde056c70a3caf3e5f3ed159a4d8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6325d43c7b48252710eda9b7aaf3c4ac0390b84315cba3a984512aa93f6f5418 0.600000000000 1610485 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": 1127688, "vin": [ { "gen": { "height": 1127678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6325d43c7b48252710eda9b7aaf3c4ac0390b84315cba3a984512aa93f6f5418" } } ], "extra": [ 1, 40, 153, 127, 158, 216, 76, 133, 6, 77, 32, 165, 112, 87, 64, 14, 182, 144, 79, 221, 224, 86, 199, 10, 60, 175, 62, 95, 62, 209, 89, 164, 216, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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