Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc90f2bae56914ffff1fd5c397fb1203c755e13cd43b2d0d4c62543b78da9f4

Tx prefix hash: bfae3873468a1f15fbd13e1e221cde5a9d12116dbc2b4336ca332328cc44e193
Tx public key: 5119b2e84209eda22d4423f5f4f6b7ac40b487693c4030f19ec9e24948592839
Timestamp: 1737290619 Timestamp [UCT]: 2025-01-19 12:43:39 Age [y:d:h:m:s]: 00:336:01:35:06
Block: 1200717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237772 RingCT/type: yes/0
Extra: 015119b2e84209eda22d4423f5f4f6b7ac40b487693c4030f19ec9e24948592839021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f284f634b6cbe55b8a01432bdb1790aa0ced2d43a078d5bc34772d438bbc14e 0.600000000000 1687362 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": 1200727, "vin": [ { "gen": { "height": 1200717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f284f634b6cbe55b8a01432bdb1790aa0ced2d43a078d5bc34772d438bbc14e" } } ], "extra": [ 1, 81, 25, 178, 232, 66, 9, 237, 162, 45, 68, 35, 245, 244, 246, 183, 172, 64, 180, 135, 105, 60, 64, 48, 241, 158, 201, 226, 73, 72, 89, 40, 57, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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