Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b36643aa3830fb380b4c6214fc3a5cf4434e2456f5288b2c6f87fde0c01b0e68

Tx prefix hash: bfe8dd3e30bac7401118b6690db43f49068889c8839f5b617273b4ce9f487601
Tx public key: 7bb9c7ed28c3467ebb5b93c9f8d7c0bc2d02ace039ed9a66a9e97db24db669ce
Timestamp: 1745795872 Timestamp [UCT]: 2025-04-27 23:17:52 Age [y:d:h:m:s]: 00:205:14:50:41
Block: 1270903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144667 RingCT/type: yes/0
Extra: 017bb9c7ed28c3467ebb5b93c9f8d7c0bc2d02ace039ed9a66a9e97db24db669ce0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebc827243d623a871541a0b1b5d28fca49d91e2acf6d07c0ed507a4bbae34348 0.600000000000 1758148 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": 1270913, "vin": [ { "gen": { "height": 1270903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebc827243d623a871541a0b1b5d28fca49d91e2acf6d07c0ed507a4bbae34348" } } ], "extra": [ 1, 123, 185, 199, 237, 40, 195, 70, 126, 187, 91, 147, 201, 248, 215, 192, 188, 45, 2, 172, 224, 57, 237, 154, 102, 169, 233, 125, 178, 77, 182, 105, 206, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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