Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe01a19fa9f5696d61a79b0d40a14f308c932640a8a8c875dacd27288b50a65

Tx prefix hash: cb97f0ab836473c8184cf844d9def6ae8ee572992111c12e14372993ce4be83a
Tx public key: 278a861ee7ebd2083d8c0db5840b1b5a801a2c0b5dea76c44b7d1be82d514219
Timestamp: 1735720626 Timestamp [UCT]: 2025-01-01 08:37:06 Age [y:d:h:m:s]: 00:303:07:29:49
Block: 1187753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214284 RingCT/type: yes/0
Extra: 01278a861ee7ebd2083d8c0db5840b1b5a801a2c0b5dea76c44b7d1be82d514219021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1129ae2a0a4390957b23afc368df7e64c886d04c4ea5fea0ea65d0b747a5cafb 0.600000000000 1674248 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": 1187763, "vin": [ { "gen": { "height": 1187753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1129ae2a0a4390957b23afc368df7e64c886d04c4ea5fea0ea65d0b747a5cafb" } } ], "extra": [ 1, 39, 138, 134, 30, 231, 235, 210, 8, 61, 140, 13, 181, 132, 11, 27, 90, 128, 26, 44, 11, 93, 234, 118, 196, 75, 125, 27, 232, 45, 81, 66, 25, 2, 17, 0, 0, 0, 2, 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